Skip to main content

What’s New

Qrvey 8.5
Version 8.5 (LTS) of the Qrvey platform is now available to customers. This version includes several new features and performance improvements.
Learn More
End-of-life Schedule
We've added a new article that lists the features and endpoints that have been scheduled for deprecation. All features and endpoints will be supported for (1) year after the release date of the LTS version that contains the alternative.
Learn More
NodeJS Deprecation
AWS has announced that it is deprecating NodeJS 12, 14, and 16. To avoid any issues as a result of this deprecation, upgrade your instances of the Qrvey platform as described in this announcement.
Learn More
Version: 8.5

Overview of Content Deployment

Content Deployment is the process of copying content from one application to another, in the same environment or to a different one. Content Deployment is a powerful tool for managing all of the content generated in a multi-tenant deployment. Some examples of where this feature may be used are:

  • Copying an application that has been created in a staging environment to the production environment.
  • Copying some content, or an entire application created by one user to other users’ accounts.
  • Releasing the new additions to a baseline application to multiple tenants of the system.
  • Provisioning a copy of a baseline application to multiple tenants of the system.

Note: This section of the Partner Portal describes how to use the Qrvey Admin Center to perform Content Deployment. This feature can also be managed using the Qrvey API. For more information, see:

To open the Content Deployment page in Qrvey Admin Center, click the Content Deployment icon in the left-hand navigation pane:
Content Deployment Icon

Content Deployment requires you to configure four steps:

  1. Servers define the source and destination instances.
  2. Packages create a snapshot copy of the source application.
  3. Deployment Definitions specify the content to copy and what to change during the deployment.
  4. Deployment Jobs specify the recipient users and the destination instances, and they determine the value of all marked tokens for each recipient or group of recipients.

Once these steps are complete, you can run the deployment job.

For a video tutorial on using Content Deployment, see Content Deployment.